-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
porting things to niquests #6023
porting things to niquests #6023
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this makes sense for how requests is used in these places. If niquests isn't as compatible as we think, we can replace with python's http.client, or aiohttp.
tbf, it really does seem to be as compatible... :) another thing i was thinking of doing was importing niquests directly, and then s/requests/niquests/g in all of the scripts... but since this work and was a much simpler change, i'm inclined to leave things as they are in this PR. |
Yeah, I thought the same thing. "niquists as requests" kind of documents why it is being used. |
i'd like to start here before fixing all of the images that have
requests
installed....i tested the python in
scripts
and things work exactly as intended. i also tested the scaler via the steps here, and again, everything is working as intended.this resolves https://github.com/berkeley-dsep-infra/datahub/security/dependabot/182